Process Types
To streamline the definition of a process, APPX categorizes the various activities that you can reasonably expect an application to perform into two groups.
Form Based Objects
Menu processes, which provide an on-screen display from which to execute selected processes. For example, a screen that lists the reports that are available in an application and from which you select a specific report is a menu process. Refer to Menu Processes for a discussion of menu specifications.
Input processes, which permit you to enter or maintain data in one or more files from designer-formatted screens and overlays. A sales order entry function and a customer file maintenance function are both input processes. Refer to Input Processes for a discussion of input specifications.
Inquiry processes, which extract a record or a specific set of records from the database, and display the information on the screen. Refer to Inquiry Processes for a discussion of inquiry specifications.
Output processes, which convey information from a database, either on the screen or in hard copy. Trial balances, product purchase history reports, and customer lists are all examples of output processes. Refer to Output Processes for a discussion of output specifications.
Processing Objects
Query processes, which determine the records that are available to a subsequent input, update, or output process, and/or establish the data?s sort hierarchy. Refer to Query Processes for a discussion of query specifications.
Update processes, which alter the database by adding records, deleting records, or changing information based on designer-established criteria. Refer to Update Processes for a discussion of update specifications.
Subroutine processes, which define reusable procedural programs that can be executed from other APPX processes. A program that converts one unit of measure to another, for example, can be written as a subroutine. Refer to Subroutine Processes for a discussion of subroutine specifications.
Job processes, which control the sequencing of other related processes. Refer to Job Processes for a discussion of job specifications.
Status processes, which interrogate the database and warn the operator of possible error conditions. Refer to Status Processes for a discussion of status specifications. |